perm filename CBCL[E82,JMC]1 blob
sn#669814 filedate 1982-07-22 generic text, type T, neo UTF8
CBCL - summer 1982
1. We need better examples of CBCL communications.
2. How about the following style: New entities, including offers
and objects, are introduced by first giving a proper name which
in itself says nothing and then giving sentences about it. This
avoids some of the problems of saying how many or what slots
the description of the entity has.
Thus "I order 500 Number 2 pencils from you" may be expressed.
(introducing a7301) ; this may not really be necessary
(purchase-order a7301)
(equal (item a7301) a7302)
(equal (type a7302) pencil)
(equal (hardness a7302) 2)
(equal (quantity a7301) 500)
We suppose that this can be the complete purchase order message.
If so, then much information is determined by default. Perhaps
if we had said (purchase-order1 a7301), it might be taken as
stated what information is determined by default or by previous
arrangement - for example, terms of payment and delivery. If
we want to specify the delivery date, we might add
(delivery-date a7301 (before (date 1982 July 30))).